Kount Overview

Kount transactions are available to Canadian integrations only.

Introduction to Kount Inquiries

There are 2 types of transactions associated with Kount:

• Kount Inquiry
• Kount Update

A risk inquiry request—can be performed either before or after performing a customer payment transaction. If performed before, the risk score will be less complete as it will not include most customer information.

Kount Update request is to alter or update the Kount Inquiry information, such as order number or payment authorization details.

To use the Kount Inquiry, you must implement the device data collector component. Data collector must have a unique session ID, the same session ID must be sent with the Kount Inquiry or Kount update.

Kount Data Collector

The Data Collector process provides data related to the device initiating the transaction, and runs in the background while the webpage loads in a client browser or mobile application. The data collected is used in conjunction with the RIS data.

Data Collector Process Flow - Kount

• Customer browses to merchant order form page containing Data Collector code
• Customer browser/mobile application automatically requests redirect on the Data Collector element
• Customer browser is redirected to Kount servers
• Kount collects device attributes
• Kount directs customer browser to display static image hosted by merchant

Data Collector Process Requirements.

1. Port 443 must be available to post and receive data from Kount
2. The code can be inserted anywhere on the webpage prior to submission of the order. For faster results you should place this code at the top of the html page coding.
3. Session ID

   The Session ID is the unique identifier for the collection event and is specific to the user’s request. You will use the Session ID for subsequent calls to the Inquiry Service

   Session ID Requirements

   • Session IDs must be unique per request. They must be unique for a minimum of 30 days.
   • Session ID must contain only alphanumeric characters (0-9, a-z or A-Z), dashes (-) or underscores (_).
   • Session ID values should be 32 characters in length. Session ID values of less than 32 characters will be accepted, but it is strongly recommended to use a 32 character value.
   
   

   Implementation Details

   We advise that you create a the session id that is sent over to Kount and this is accomplished by creating the session ID that meets the criteria described below and including that in the call to download the Device Data Collection SDK (web implementation only). Assuming the session ID used in this example is abcdefg12345abababab123456789012, the call to download the SDK looks like this:

   

4. Web Client and Browser Set Up

The Data Collector runs on a client’s browser and collects a variety of information that helps uniquely identify the device.  There are four high level integration steps required:

1. Download the Kount Device Data Collection SDK

   The Kount Device Data Collection SDK is hosted by Kount, and needs to be downloaded dynamically to be used on a web page.

   The following code can be used to download the SDK:

   

   Variable	Description
   m	Six digit Merchant ID number issued by Kount
   s	32 character session ID Exclude this parameter from the call to the download of the SDK to have Kount generate a session ID for you.
   DATA\_COLLECTOR\_URL	The URLs for the Data Collector are Environment specific. There is a URL for Test and a URL for Production

   
   

   DATA_COLLECTOR URL:

   Sandbox: https://tst.kaptcha.com

   Production: https://ssl.kaptcha.com

2.  Content Security Policy

   If your organization has instituted a Content Security Policy on your website that interferes with the execution of the Device Data Collection on your site, you will need to add this to your page.

3. Configure the Trigger

   The Device Data Collector SDK collection process is triggered asynchronously by the ‘load’ data-event. This gives the collector the most available time to complete its work. The collection is bound to the page load event by adding the kaxsdc class and data-event=‘load’ to an HTML element, such as the HTML body or a div. It looks something like this:

   

4. Configure the Client

   The Kount collector JavaScript is namespaced under the ka JavaScript object. It is required to have the above /collect/sdk script tag added to your page, which will import the Device Data Collector SDK.

   To start using the Device Data Collector SDK:

   • Create a new ClientSDK object

   

   • Optionally Setup Callback Methods

   The SDK provides a client programmable callback system that allows the client to execute custom code at certain points in the data collection process. This method allows a merchant to add a callback function to be called at a specified life-cycle hook. A merchant can pass a JavaScript object containing one or more life cycle hooks with a function pointer or an anonymous function to be executed.

   List of hooks (In order of firing):

   • collect-begin - Triggers when the collection starts
   • collect-end - Triggers when the collection ends
   
   

   When executed, the callback function is passed a JavaScript object containing the following properties:

   • MercSessId – The session ID used in the collection
   • MerchantId – The merchant Id
   
   

   

   • Auto Load Events

   Call the autoLoadEvents method on the client to attach the collection process to be automatically triggered by the page elements load event with the className “kaxsdc" configured in Step 3.

   

5. Code Example

   This code is an example of where each of the components discussed above appear in the web page. Use this example to help you understand where to best integrate into your website.

   NOTE: It is recommended that the Data Collector code exist at the top of the page load so it has adequate time to run before a user finishes their interaction with the webpage.

   

   

   

Native iOS and Android SDKs

The implementation of the Device Data Collector is different for native Mobile Apps. Kount has native Mobile SDKs for both iOS and Android. These SDKs can be used with all current Kount products. The native Mobile SDKs collect more data and increase the reliability of the Device ID across the life of a device. Choose the links below for more information.

iOS SDK

Installing & Configuring the SDK, and Samples.

https://github.com/Kount/kount-ios-sdk

Android SDK

Installing & Configuring the SDK, and Samples.

https://github.com/Kount/kount-android-sdk

Kount Inquiry

A risk inquiry request—can be performed either before or after performing a customer payment transaction. If performed before, the risk score will be less complete as it will not include most customer information.

Canada Code Sample

import java.io.*; 
import java.util.*;
import java.net.*;

import JavaAPI.*;

public class TestKountInquiry
{
  public static void main(String args[]) throws IOException
  {

/********************** Request Variables ****************************/

        String host = "esqa.moneris.com";
        String store_id = "moneris";
        String api_token = "hurgle";
        
        KountInquiry kountInquiry = new KountInquiry();
        
                kountInquiry.setKountMerchantId("760000"); //6 digit - This is a UNIQUE local identifier used by the merchant to identify the kount inquiry request
		kountInquiry.setKountApiKey("eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiI3NjAwMDAiLCJhdWQiOiJLb3VudC4xIiwiaWF0IjoxNTU4MDQwODQ5LCJzY3AiOnsia2EiOm51bGwsImtjIjpmYWxzZSwiYXBpIjp0cnVlLCJyaXMiOnRydWV9fQ.y3_2yzd11-Y_F6_xzVsXI-NO1a7P6ldMjDnKzl5yBko"); //214 character max - This is a UNIQUE local identifier used by the merchant to identify the kount inquiry request
		kountInquiry.setOrderId("nqa-orderidkount-1"); //64 characters max - This is a UNIQUE local identifier used by the merchant to identify the transaction e.g. purchase order number.
		kountInquiry.setCallCenterInd("N"); //Y or N - Risk Inquiry originating from call center environment
		kountInquiry.setCurrency("CAD"); //country of currency submitted on order
		kountInquiry.setDataKey("3B1C19fgfRObNHaQh5qVCpRW2"); //token from moneris vault service to represent pan if previously tokenized
		kountInquiry.setEmail("test@gmail.com"); //email address submitted by the customer
		kountInquiry.setCustomerId("NQA"); //Merchant assigned account number for consumer
		kountInquiry.setAutoNumberId("NQA-X1"); //Automatic Number Identification (ANI) submitted with order
		kountInquiry.setFinancialOrderId("nqa-fin-orderid-1"); //32 characters max - This is a local identifier used by the merchant to identify the transaction e.g. purchase order number.
		kountInquiry.setPaymentToken("4242424242424242"); //payment token submitted by merchant (ie: credit card, payer ID)
														   /*	Payment Type Must be one of the following values:
															   APAY-­Apple Pay
															   CARD-­Credit Card
															   PYPL-­PayPal
															   NONE-­None
															   GOOG-­Google Checkout
															   GIFT-­Gift Card
															   INTERAC-­Interac
															   CHEK - Check
															   GDMP - Green Dot Money Pack
															   BLML - Bill Me Later
															   BPAY - BPAY
															   NETELLER - Neteller
															   GIROPAY - GiroPay
															   ELV - ELV
															   MERCADE_PAGO - Mercade Pago
															   SEPA - Single Euro Payments Area
															   CARTE_BLEUE - Carte Bleue
															   POLI - POLi
															   Skrill/Moneybookers - SKRILL
															   SOFORT - Sofort
														   */
		kountInquiry.setPaymentType("CARD"); //payment type submitted by merchant
		kountInquiry.setIpAddress("192.168.2.1"); //Dotted Decimal IPv4 address that the merchant sees coming from the customer
		kountInquiry.setSessionId("xjudq804i1049jkjakdad"); //unique session id.  Must be unique over a 30-day span
		kountInquiry.setWebsiteId("DEFAULT");
		kountInquiry.setAmount("100"); //Transaction amount This must contain at least 3 digits, two of which are penny values
		kountInquiry.setPaymentResponse("A"); //A - Authorized, D - Declined - payment transaction response
		kountInquiry.setAvsResponse("M"); //M - Match, N - No Match - avs verification response returned from payment request. This can be provided should kountInquiry be performed after the transaction is complete
		kountInquiry.setCvdResponse("M"); //M - Match, N - No Match, X - Unsupported/Unavailable - cvd response returned to merchant from processor. This can be provided should kountInquiry be performed after the transaction is complete
		kountInquiry.setBillStreet1("3300 Bloor Street"); //billing street address line 1
		kountInquiry.setBillStreet2("West Tower"); //billing street address line 2
		kountInquiry.setBillCountry("CA"); //2 character - billing country code
		kountInquiry.setBillCity("Toronto"); //billing address city
		kountInquiry.setBillPostalCode("M8X2X2"); //billing address postal code
		kountInquiry.setBillPhone("4167341000"); //billing phone number
		kountInquiry.setBillProvince("ON"); //billing address province
		kountInquiry.setDob("1950-11-12"); //YYYY-MM-DD
		kountInquiry.setEpoc("1491783223"); //timestamp expressed as seconds from epoch
		kountInquiry.setGender("M"); //M - Male or F - Female
		kountInquiry.setLast4("4242"); //last 4 digits of credit card value
		kountInquiry.setCustomerName("Moneris Test"); //customer name submitted with the order
		kountInquiry.setShipStreet1("3200 Bloor Street"); //shipping street address line 1
		kountInquiry.setShipStreet2("East Tower"); //shipping street address line 2
		kountInquiry.setShipCountry("CA"); //2 digit - shipping country code
		kountInquiry.setShipCity("Toronto"); //shipping address city
		kountInquiry.setShipEmail("test@gmail.com"); //email of recipient
		kountInquiry.setShipName("Moneris Test"); //name of recipient
		kountInquiry.setShipPostalCode("M8X2X3"); //shipping address postal code
		kountInquiry.setShipPhone("4167341001"); //ship-to phone number
		kountInquiry.setShipProvince("ON"); //shipping address province
		kountInquiry.setShipType("ST"); //Same Day = SD, Next Day = ND, Second Day = 2D, Standard = ST

		//Product Details - item number, product_type, product_item (SKU), product_description, product quatity, product_price
		//1-25 products can be added - must be in sequence starting with 1
		kountInquiry.setProduct(1, "Phone", "XM9731S", "iPhone 7", "1", "100");
		kountInquiry.setProduct(2, "Phone", "YM9731R", "iPhone 6", "1", "100");

		//Local Attributes - 255 character max each,These attributes can be used to pass custom attribute data. These are used if you wish to correlate some data with the returned response via kount
		//1-25 of these can be submitted in one request - must be in sequence starting with 1
		kountInquiry.setUdfField("LOCAL_ATTRIBUTE_1", "iPhone 7");
		kountInquiry.setUdf();

        //Standard Post Request
        KountHttpsPostRequest mpgReq =
	            new KountHttpsPostRequest(host, store_id, api_token, kountInquiry);
	            		
        //Optionally Post Request via Proxy
        /*String proxyHost = "";
        String proxyPort = "";
        String proxyUser = "";
        String proxyPassword = "";

		KountHttpsPostRequest mpgReq =
        	new KountHttpsPostRequest(host, store_id, api_token, kountInquiry, proxyHost,proxyPort, proxyUser, proxyPassword);*/
        
		try
        {
			KountReceipt[] kountReceipt = mpgReq.getKountReceipts();
			
			for (int i = 0;i<kountReceipt.length;i++)
            {
				System.out.println("ResponseCode = " + kountReceipt[i].getResponseCode());
				System.out.println("ReceiptId = " + kountReceipt[i].getReceiptId());
				System.out.println("Message = " + kountReceipt[i].getMessage());
				System.out.println("KountResult = " + kountReceipt[i].getKountResult());
				System.out.println("KountTransactionId = " + kountReceipt[i].getKountTransactionId());
				System.out.println("KountScore = " + kountReceipt[i].getKountScore());
				System.out.println("KountInfo = " + kountReceipt[i].getKountInfo());
            }
        }
        catch (Exception e)
        {
            e.printStackTrace();
        }
  }
} // end TestKountInquiry example

                

Kount Inquiry transaction object definition

KountInquiry kountInquiry = new KountInquiry();

HttpsPostRequest object for Kount Inquiry transaction

HttpsPostRequest mpgReq = new HttpsPostRequest();

mpgReq.setTransaction(kountInquiry);

Kount Inquiry object mandatory values

Kount Inquiry object optional values

Kount Update

This transaction is done to request to update the Kount risk inquiry information, such as order number and payment authorization details.

Canada Code Sample

import java.io.*; 
import java.util.*;
import java.net.*;

import JavaAPI.*;

public class TestKountUpdate
{
  public static void main(String args[]) throws IOException
  {

/********************** Request Variables ****************************/

        String host = "esqa.moneris.com";
        String store_id = "moneris";
        String api_token = "hurgle";

        KountUpdate kountUpdate = new KountUpdate ();
        
        kountUpdate.setKountTransactionId("PHJS0J2PK1MB"); //kount transaction ID number that is returned in the response of a kount_inquiry request
		kountUpdate.setKountMerchantId("760000"); //6 digit - This is a UNIQUE local identifier used by the merchant to identify the kount inquiry request
		kountUpdate.setKountApiKey("eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiI3NjAwMDAiLCJhdWQiOiJLb3VudC4xIiwiaWF0IjoxNTU4MDQwODQ5LCJzY3AiOnsia2EiOm51bGwsImtjIjpmYWxzZSwiYXBpIjp0cnVlLCJyaXMiOnRydWV9fQ.y3_2yzd11-Y_F6_xzVsXI-NO1a7P6ldMjDnKzl5yBko"); //214 character max - This is a UNIQUE local identifier used by the merchant to identify the kount inquiry request
		kountUpdate.setOrderId("nqa-orderidkount-5"); //64 characters max - This is a UNIQUE local identifier used by the merchant to identify the transaction e.g. purchase order number.
		kountUpdate.setFinancialOrderId("nqa-fin-orderid-1"); //32 characters max - This is a local identifier used by the merchant to identify the transaction e.g. purchase order number
		kountUpdate.setDataKey("3B1C19fgfRObNHaQh5qVCpRW2"); //token from moneris vault service to represent pan if previously tokenized
		kountUpdate.setPaymentToken("4242424242424242"); //payment token submitted by merchant (ie: credit card, payer ID)
								/*	Payment Type Must be one of the following values:
								APAY-­Apple Pay
								CARD-­Credit Card
								PYPL-­PayPal
								NONE-­None
								GOOG-­Google Checkout
								GIFT-­Gift Card
								INTERAC-­Interac
								CHEK - Check
								GDMP - Green Dot Money Pack
								BLML - Bill Me Later
								BPAY - BPAY
								NETELLER - Neteller
								GIROPAY - GiroPay
								ELV - ELV
								MERCADE_PAGO - Mercade Pago
								SEPA - Single Euro Payments Area
								CARTE_BLEUE - Carte Bleue
								POLI - POLi
								Skrill/Moneybookers - SKRILL
								SOFORT - Sofort
								*/
		kountUpdate.setPaymentType("CARD"); //payment type submitted by merchant
		kountUpdate.setSessionId("xjudq804i1049jkjakdad");  //unique session id.  Must be unique over a 30-day spa
		kountUpdate.setPaymentResponse("A"); //A - Authorized, D - Declined - payment transaction response
		kountUpdate.setAvsResponse("M"); //M - Match, N - No Match - avs verification response returned from payment request. This can be provided should kount_inquiry be performed after the transaction is complete
		kountUpdate.setCvdResponse("N"); //M - Match, N - No Match, X - Unsupported/Unavailable - cvd response returned to merchant from processor. This can be provided should kount_inquiry be performed after the transaction is complete
		kountUpdate.setLast4("4242"); ////last 4 digits of credit card value
		kountUpdate.setEvaluate("Y"); //Y or N - If set to Y, full re-evaluation will be performed with Kount.  If unset, default value is N
		kountUpdate.setRefundStatus("C"); //R = Refund, C = Chargeback		
		
        //Standard Post Request
        KountHttpsPostRequest mpgReq =
	            new KountHttpsPostRequest(host, store_id, api_token, kountUpdate);
        
        /*Optionally Post Request via Proxy
        String proxyHost = "";
        String proxyPort = "";
        String proxyUser = "";
        String proxyPassword = "";

		KountHttpsPostRequest mpgReq =
        	new KountHttpsPostRequest(host, store_id, api_token, kountUpdate, proxyHost,proxyPort, proxyUser, proxyPassword);*/
		
		try
        {
			KountReceipt[] kountReceipt = mpgReq.getKountReceipts();
			
			for (int i = 0;i<kountReceipt.length;i++)
            {
				System.out.println("ResponseCode = " + kountReceipt[i].getResponseCode());
				System.out.println("ReceiptId = " + kountReceipt[i].getReceiptId());
				System.out.println("Message = " + kountReceipt[i].getMessage());
				System.out.println("KountResult = " + kountReceipt[i].getKountResult());
				System.out.println("KountTransactionId = " + kountReceipt[i].getKountTransactionId());
				System.out.println("KountScore = " + kountReceipt[i].getKountScore());
				System.out.println("KountInfo = " + kountReceipt[i].getKountInfo());
            }
        }
        catch (Exception e)
        {
            e.printStackTrace();
        }
        
  	}
} // end TestKountUpdate example

                

Kount Update transaction object definition

KountUpdate kount_update = new KountUpdate();

HttpsPostRequest object for Kount Update transaction

HttpsPostRequest mpgReq = new HttpsPostRequest();

mpgReq.setTransaction(kount_update);

Kount Update object mandatory values

Kount Update transaction optional values

Definition of Request Fields

Definition of Response Fields

Error Messages

Error messages that are returned if the gateway is unreachable

Global Error Receipt

You are not connecting to our servers. This can be caused by a firewall or your internet connection.

Response Code = NULL

The response code can be returned as null for a variety of reasons. The majority of the time, the explanation is contained within the Message field.
When a ‘NULL’ response is returned, it can indicate that the issuer, the credit card host, or the gateway is unavailable. This may be because they are offline or because you are unable to connect to the internet.
A ‘NULL’ can also be returned when a transaction message is improperly formatted.

Error messages that are returned in the Message field of the response

XML Parse Error in Request: <System specific detail>

An improper XML document was sent from the API to the servlet.

XML Parse Error in Response: <System specific detail>

An improper XML document was sent back from the servlet.

Transaction Not Completed Timed Out

Transaction timed out before the host responds to the gateway.

Request was not allowed at this time

The host is disconnected.

Could not establish connection with the gateway: <System specific detail>

Gateway is not accepting transactions or server does not have proper access to internet.

Input/Output Error: <System specific detail>

Servlet is not running.

The transaction was not sent to the host because of a duplicate order id

Tried to use an order id which was already in use.

The transaction was not sent to the host because of a duplicate order id

Expiry Date was sent in the wrong format.

Vault error messages

Can not find previous

Data key provided was not found in our records or profile is no longer active.

Invalid Transaction

Transaction cannot be performed because improper data was sent.

or

Mandatory field is missing or an invalid SEC code was sent.

Malformed XML

Parse error.

Incomplete

Timed out.

or

Cannot find expiring cards.

Custom Android Pay In-App SDK Responses

Response Codes for Kount

Security Requirements

All Merchants and Service Providers that store, process, or transmit cardholder data must comply with PCI DSS and the Card Association Compliance Programs. However, validation requirements vary by business and are contingent upon your "Merchant Level" or "Service Provider Level". Failure to comply with PCI DSS and the Card Association Compliance Programs 3.2 may result in a Merchant being subject to fines, fees or assessments and/or termination of processing services. Non-compliant solutions may prevent merchants boarding with Moneris Solutions.

As a Moneris Solutions client or partner using this method of integration, your solution must demonstrate compliance to the Payment Card Industry Data Security Standard (PCI DSS) and/or the Payment Application Data Security Standard (PA DSS) 3.2. These standards are designed to help the cardholders and merchants in such ways as they ensure credit card numbers are encrypted when transmitted/stored in a database and that merchants have strong access control measures, logging, secure software updates, secure remote access and support.

For further information on PCI DSS and PA DSS requirements, please visit www.pcisecuritystandards.org.

For more information on how to get your application PCI-DSS compliant, please contact our Integration Specialists and visit https://developer.moneris.com to view the PCI-DSS Implementation Guide.

Testing Moneris Kount Integration & QA Credentials

A testing environment is available for you to connect to while you are integrating your site to the Moneris Gateway. The Moneris Gateway QA environment is generally available 24/7, however since it is a test environment we cannot guarantee 100% availability.  When using the APIs in the test environment you will need to use test versions of the Kount Merchant ID, SITE ID and Kount API token. The test values of these variables are different based on the Kount package you have purchased.

To begin testing for the Moneris Kount Essential Solution:

1. Insert the test Kount merchant credentials below:

   kount_merchant_id – 760000

   kount_api_key –

   eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiI3NjAwMDAiLCJhdWQiOiJLb3VudC4xIiwiaWF0IjoxNTU4MDQwODQ5LCJzY3AiOnsia2EiOm51bGwsImtjIjpmYWxzZSwiYXBpIjp0cnVlLCJyaXMiOnRydWV9fQ.y3_2yzd11-Y_F6_xzVsXI-NO1a7P6ldMjDnKzl5yBko

   website_id – BASIC1

2. Insert your test Store ID into the value for store_id; for information on how to get your Store ID and API token, see Testing A Solution or Request a Custom QA Account.
3. Insert your test API token into the value for api_token.
4. Change the host URL to the Moneris Gateway test URL at https://esqa.moneris.com.

To begin testing for the Moneris Kount Enterprise Solution:

1. Insert the test Kount merchant credentials provided to you by your Kount Client Success Manager:

   kount_merchant_id – provided by Kount Client Success Manager

   kount_api_key –  provided by Kount Client Success Manager

   website_id – provided by Kount Client Success Manager

2. Insert your test Store ID into the value for store_id; for information on how to get your Store ID and API token, see Testing A Solution or Request a Custom QA Account.
3. Insert your test API token into the value for api_token.
4. Change the host URL to the Moneris Gateway test URL at https://esqa.moneris.com.

Moneris Kount Production Credentials

For merchants using the Moneris Kount Essential solution please e-mail api@moneris.com to obtain your production Kount MID, Kount API Key and website ID (SITE ID) credentials.

For merchants using the Moneris Kount Enterprise solution your Kount credentials (Kount MID, Kount API Key and website ID) will be provided by your Kount Client Success Manager.

Moneris Kount Enterprise Test Script

It is recommended that you use test scripts to validate data is coming to Kount as expected and to prove out expected actions within your Order Management System (OMS) based on the response or reply from Kount.

Below are some examples and actions you may wish to undertake to validate your data submission and the actions within Kount and your systems based upon the Kount responses. These are all optional, but highly recommended.

While some of these examples are for how to set up items in the system, others are recommendations of order details to submit to test functionality and set up.

Below is a list of the items we recommend you test and set up:

1. Create and verify UDFs
2. Device Data Collection
3. Customer Email Address
4. Merchant Order Number
5. Shopping Cart Information
6. Address and Phone
7. Payment information
8. Test VIP List Changes

1 Create and verify UDFs

For merchants who intend to pass additional data into Kount in the form of a User Defined Field (UDF) you must create appropriate "label" entries in the Kount Agent Web Console (AWC).

To create a UDF, do the following:

1. In the Agent Web Console (AWC), click the Fraud Control tab, and then click User Defined Fields.
2. On the User Defined Fields page, in the lower right, click Add UDF.
3. In the Add UDF box, enter the name of the UDF in the Label text box. A label can be a maximum of 28 characters and the first character must be a letter.
4. Type a description in the Description field.
5. Select Number, Alpha-Numeric, Date, or Amount from the Type drop-down menu. Note: UDFs intended for use in a VIP list must be alpha-numeric.
6. Click Save UDF.

2 Device Data Collection

The Risk Inquiry Service (RIS) joins device data provided from the data collector process with the customer order data sent from the merchant. Once the device data and the order data are combined, RIS evaluates and scores each transaction.

It should be verified below, on the transaction details page, that the device data collector is functioning properly and that a unique session ID is being passed to Kount in each Risk Inquiry.